This section lists some frequently asked questions
about the iDRAC Service Module.
Do I need to uninstall
OpenManage Server Administrator before installing or running the
iDRAC Service Module?
No. Before you install or run the iDRAC
Service Module, ensure that you have stopped the features of OpenManage Server
Administrator that the iDRAC Service Module provide.
-
NOTE: Uninstalling the OpenManage Server
Administrator is not required.
How do I know that
the iDRAC Service Module is installed in my system?
To know
if the iDRAC Service Module is installed on your system,
-
On Windows:
Run the
service.msc command. Find from the list of services if there is a service by
name
DSM iDRAC Service Module.
-
On Linux:
Run the command
/etc/init.d/dcismeng status. If the iDRAC Service Module
is installed and running, the status displayed will be
running.
-
NOTE: Use the
systemctl status dcismeng.service command instead of the
init.d command to check if the iDRAC Service Module is installed
on RedHat Enterprise Linux 7 and SUSE Linux Enterprise 12 operating
system.
How do I know which
version of the iDRAC Service Module I have in my system?
To
check the version of the iDRAC Service Module in the system, click
. The version
of the installed iDRAC Service Module will be listed in the
Version tab. You can also check the version by go to
.
What is the minimum
permission level required to install the iDRAC Service Module?
To install the iDRAC Service Module, you must have operating system Administrator
level privileges.
Whenever I try to install
the iDRAC Service Module, it shows an error message
This
is not a supported server
. Consult the User Guide for
additional information about the supported servers. What should I
do now?
Before installing the iDRAC Service Module, ensure
that the server or the system on which the iDRAC Service Module is
to be installed is a Dell’s 12
th generation PowerEdge server
or later. Also make sure that you have a 64-bit system.
I see the message
The iDRAC Service Module is unable to communicate with iDRAC using
the OS to iDRAC Pass-through channel
in the OS log, even
when the OS to iDRAC Pass-through over USBNIC is configured properly.
Why do I get this message?
iDRAC Service Module uses the OS
to iDRAC Pass-through over USBNIC to establish communication with
iDRAC. Sometimes, the communication is not established though the
USBNIC interface is configured with correct IP endpoints. This may
happen when the host OS routing table has multiple entries for the
same destination mask and the USBNIC destination is not listed as
the first one in routing order.
Table 1. Details.
The following table provides information about
the routing order.
Destination |
Gateway |
Genmask |
Flags |
Metric |
Ref |
Use Iface |
default |
10.94.148.1 |
0.0.0.0 |
UG |
1024 |
0 |
0 em1 |
10.94.148.0 |
0.0.0.0 |
255.255.255.0 |
U |
0 |
0 |
0 em1 |
link-local |
0.0.0.0 |
255.255.255.0 |
U |
0 |
0 |
0 em1 |
link-local |
0.0.0.0 |
255.255.255.0 |
U |
0 |
0 |
0 enp0s20u12u3 |
In the example
enp0s20u12u3 is the USBNIC interface.
The link-local destination mask is repeated and the USBNIC is not
the first one in order. This results in the connectivity issue between
iDRAC Service Module and iDRAC over the OS to iDRAC Pass-through.
To troubleshoot the connectivity issue, you can perform one of the
following steps:
Ensure that the iDRAC USBNIC IPv4
address (by default it’s 169.254.1.1) is reachable from the host OS.
If not:
-
Change the iDRAC USBNIC address on a unique destination
mask.
-
Delete the unwanted entries from the routing table
to ensure USBNIC is chosen by route when the host wants to reach the
iDRAC USBNIC IPv4 address.
Whenever I try to install
the iDRAC Service Module, an error message This operating system is
not supported is displayed.
The iDRAC Service Module can be
installed only on the supported operating systems. For information
on operating systems that are supported, see
Supported operating
systems
.
I used the remote iDRAC
hard reset feature to reset the iDRAC. However, the IPMI is
unresponsive and I am not able to troubleshoot.
If you try
to use the remote iDRAC hard reset feature on
VMware ESXi 5.5 U3 or
ESXi 6.0 U1, the IPMI drivers becomes unresponsive, because
of this the iDRAC Service Module communication is stopped. You may
have to reboot the server and load the IPMI driver again to resolve
the issue.
Where do I find the
Replicated LifeCycle log on my Operating System?
To view the
replicated LifeCycle logs:
Table 2. Frequently asked
question
.
Operating system location.
Operating
System
|
Location |
Microsoft Windows |
<Existing group or Custom folder>
. All the iDRAC
Service Module LifeCycle logs are replicated under the source name
iDRAC Service Module.
|
Red Hat Enterprise Linux, SUSE
Linux, CentOS, and Citrix XenServer
|
/var/log/messages
|
VMware ESXi |
/var/log/syslog.log
|
What is the default
SNMP protocol configured in iDRAC Service Module to send alerts in
Linux operating systems?
By default, the SNMP multiplexing
protocol (SMUX) is configured in iDRAC Service Module to send alerts.
SMUX is not supported
on my system. Which protocol should I configure to send alerts?
If SMUX is not supported on your system, Agent-x is used as a default
protocol.
How do I configure
iDRAC Service Module to use the Agent-x protocol to send alerts by
default?
You can configure Agent-x as the default protocol
using
./Enable-iDRACSNMPTrap.sh 1/agentx –force command.
If
–force is not specified, ensure
that the net-SNMP is configured and restart the snmpd service.
What are the Linux-dependent
packages or executables I should install while completing the Linux
installation?
To see the list of Linux-dependent packages,
see
Linux dependencies.
I created a custom
folder in Windows Event Viewer, but the LC logs are not replicated
in my custom folder. What do I have to do now to replicate the LC
logs?
Ensure to close the Windows
Event Viewer after
creating the custom folder. Open the Windows
Event Viewer again
to view the replicated LC logs.
I chose custom install
option from the Graphical User Interface during iDRAC Service Module
installation and disabled a feature, but I am not able to enable the
feature using any of the other interfaces. How do I enable the feature
again?
On systems running Microsoft Windows operating system,
a feature that is enabled using the installer and disabled using any
interface other than the installer, can only be enabled using the
same interface or the installer in Graphical User Interface mode.
For example, you may not be able to enable a feature
using the RACADM CLI commands, that was disabled from the Graphical
User Interface during iDRAC Service Module installation.
I am not able to access
the iDRAC page through the host OS as an Active Directory user over
LDAP. I am trying to access the iDRAC page through the host OS, but
I get an error saying that the site cannot be reached. How do I troubleshoot
the issue?
When you are trying to access the
iDRAC page through the host OS, you may get an error saying that the
site cannot be reached. Ensure that the iDRAC network is configured
for authentication as an LDAP user. You can also login as a local
user or a guest.
I am not able to access
the iDRAC page through the host OS after performing an iDRAC factory
reset operation, such as
racadm racresetcfg. How do I troubleshoot the issue?
Ensure that
the OS to iDRAC passthru channel is enabled. By default, it is disabled
in factory mode. To enable the OS to IDRAC passthru channel on iDRAC,
use the following command,
racadm set idrac.os-bmc.adminstate
1
.
I am seeing 169.254.0.2
as the source IP address in the iDRAC SNMP trap received via iSM.
How do I troubleshoot the issue?
On Linux OS,
the iDRAC SNMP traps received via Host OS displays the hostname or
source IP address as 169.254.0.2 instead of the actual Host OS name
or IP address. This is decided by the OS to populate the entry before
rendering the trap to the user.
I have configured OS
to iDRAC pass-through to LOM and when I try to run dcism-sync, the
update operation fails. What can be done?
OS
to iDRAC pass-through should be configured to USB-NIC mode. This is
a pre-requisite for iDRAC Service Module installation and update.
When Hyper-V is enabled in the Host OS, iSM is unable to communicate with iDRAC. What should I do?
Enable the remote NDIS device under
Network Adapter.
I am able to enable or disable the WMIInfo feature of iSM on Linux and VMware ESXi Operating Systems using racadm and WSMAN
commands. Does this impact my iSM configuration on the Host OS?
The WMIInfo feature of iSM is applicable only for Microsoft Windows Operating Systems. However, enabling or disabling this
feature from any of the iDRAC interfaces on any Operating System other than Microsoft Windows does not impact the iSM configuration
on the Host OS.
If I delete the IP address of the USBNIC interface on the Host OS, then iSM is unable to communicate with iDRAC.
Starting iSM version 3.3, iSM configures the Host OS USBNIC interface only once. Subsequently, if you bring down the USBNIC
interface on the Host OS by deleting the IP address, making the interface link down or disabling the IPV4 or IPV6 address
on this interface, then iSM will retain the user configuration and does not override the interface settings. To restore the
communication between iSM and iDRAC, please restart the iSM service on the Host OS.
After installing iSM using the Batch file
ISM_Win.BAT from the iDRAC exposed logical partition "SMINST" on Microsoft Windows OS, I see a console message saying "The system cannot
find the file specified."
After iSM is installed successfully, the logical partition
SMINST gets unmounted from the Host OS. This message appears if the BAT script is invoked from the
SMINST partition itself. The installation is successful. No action is required by the user.
If dependent packages for iSM are not present on Ubuntu OS, then installation through OS DUP installs iSM in install+unpacked
state. You can verify this using the below command:
#dpkg -s dcism
Package: dcism
Status: install ok unpacked
To fix this issue, run the command
apt-get install -f. This will install dependent packages.
When I install iSM 3.4.0 on Linux operating systems such as RedHat Enterprise Linux, I see some messages in OS logs such as
G_IS_SIMPLE_ACTION (simple)' failed: failed to rescan: Failed to parse /usr/share/applications/iDRACGUILauncher.desktop file:
cannot process file of type application/x-desktop
.
The messages are related to the GNOME desktop manager. Various OS groups have Bugzilla items for this scenario to be addressed.
For example:
https://bugzilla.redhat.com/show_bug.cgi?id=1594177. No action is required by the user.
I see a blank terminal on RHEL 6.10 or RHEL 7.6 when I click on
iDRAC GUI Launcher shortcut from
The visibility of text on the terminal depends on GNOME version on the resident OS. An alternative is to run the launcher
from a GUI-capable shell. For example:
bash#> sh /opt/dell/srvadmin/iSM/bin/iDRACLauncher.sh as a sudo user.
In case, the OS-to-iDRAC Passthru is disabled in iDRAC, the user will see a blank terminal when iDRAC GUI is launched from
the Linux OS such as RHEL 6.10 and RHEL 7.6. Select
y or
Y, and press
Enter to indicate configuration of USBNIC interface on the Host OS.
Alternatively, you can enable the OS-to-iDRAC Passthru in iDRAC in USBNIC mode and re-run the iDRAC launcher from the Host
OS.